Release Notes

June 2018

What's New

Our June 2018 release provides administrators with three new device management features: App Management for Android; VPN Configuration capabilities for both iOS and Android; and a Passcode Policy Library. There is also a new prerequisite for Android device enrollment and Android app management.

  • App Management for Android lets device administrators manage and push both free App Store apps as well as custom apps (i.e., enterprise apps) to Android devices.
  • VPN capabilities let device administrators manage VPN configurations for iOS immediately in KACE Cloud MDM, while VPN configurations for Android require enrollment in App Management for Android to allow 3rd party VPN app setup.
  • The Passcode Policy Library simplifies the management of passcode policies that can be applied to a set of devices.
  • Managed Google Play Organization prerequisite: A system administrator must link their KACE Cloud MDM account with their Managed Google Play Organization to enable Android enrollment and Android app management moving forward.

New Feature: App Management for Android

App management for Android lets an administrator approve, push, and configure apps for their Android devices. It also requires integration with Google's Enterprise Mobility Manager (EMM). Custom app publishing is also available—to use that functionality, an administrator must give the KACE Cloud MDM agent permission to publish apps using their Google Play developer account. See Link Managed Google Play Organization

New Feature: VPN Configuration

iOS - VPN Configuration for iOS lets administrators create, manage, and remove VPN Configurations in KACE Cloud MDM. For iOS, the protocols that are currently supported include: IKEv2, IPsec, L2TP, Cisco AnyConnect, SonicWall Mobile Connect, CheckPoint Mobile VPN, and F5 SSL.

Android - VPN Configuration for Android works by configuring 3rd party VPN apps that support managed configurations. An admin will need to enable App Management for Android before a VPN app can be configured. Once app management is in place, an administrator can configure and push/approve apps via KACE Cloud MDM and the managed Google Play store. See VPN Configuration - Android

New Feature: Passcode Policy Library

In the new passcode policy library, admins can create and save new policies that can be applied to a set of devices. Future passcode policy changes can then be managed by updating a single configuration. Note: If you have previously applied passcode restrictions to any of your devices, those restrictions will remain in place. See Passcode Policy Configuration

New Prerequisite: Managed Google Play Organization

As of the June 2018 release, a system administrator must link their KACE Cloud MDM account with their Managed Google Play Organization to enable Android enrollment and Android app management. Accounts for existing enrolled Android devices are automatically created when the Managed Google Play Organization is linked. In addition, the previous rule requiring an end user to add their own personal account to the managed profile to ensure agent updates via Google Play is no longer applicable. Once the Android work account is provisioned, the personal account can be removed. See Link Managed Google Play Organization

Known Issues

Role Management and SSO Configuration

If user role assignment is set to Automatic during SSO Configuration, a manual attempt to update an individuals user's role via the Users > Edit User path may appear possible, but will be overwritten by the original SSO Configuration. To resolve, the configuration setting can be changed to Manual, which will then enable editing of individual user roles.

Android Considerations

Change in Android Enrollment

In order to receive account profiles on an Android device, the KACE Cloud MDM agent app will need to be updated to the latest version available in the Google Play Store, and the device will need to be re-enrolled. This should be a one-time re-enrollment process that will allow the agent app to create a Work Profile on the device.

Gmail App

Android devices require the Gmail app to be installed in order to use the email account configurations.

Set Passcode Command

The Set Passcode function changed in Android N and later. On versions before N, an administrator could set the passcode as desired. On Android N and later, the passcode can only be set on devices that do not already have a passcode set. The user interface does not currently warn users who are attempting to set a passcode on Android N or later.

iOS Considerations

Factory Reset - Apple iOS iCloud Account Lock

When resetting an Apple iOS device back to factory defaults, the device will remain locked to the associated iCloud account. To prevent this from happening, before resetting the device, manually turn off the 'Find my phone' feature on the iPhone.

 

Additional Resources

Getting Started with KACE Cloud MDM

 

© 2018 Quest Software Inc.

ALL RIGHTS RESERVED.

 

This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software Inc.

 

The information in this document is provided in connection with Quest Software products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest Software products. EXCEPT AS SET FORTH IN THE TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST SOFTWARE ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST SOFTWARE BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST SOFTWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest Software makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest Software does not make any commitment to update the information contained in this document.

 

If you have any questions regarding your potential use of this material, contact:

Quest Software Inc.

Attn: LEGAL Dept.

4 Polaris Way

Aliso Viejo, CA 92656

Refer to our website (www.quest.com) for regional and international office information.

 

Patents

Quest Software is proud of our advanced technology. Patents and pending patents may apply to this product. For the most current information about applicable patents for this product, please visit our website at www.quest.com/legal.

Trademarks

Quest and the Quest logo are trademarks and registered trademarks of Quest Software Inc. in the U.S.A. and other countries. For a complete list of Quest Software trademarks, please visit our website at www.quest.com/legal. All other trademarks, servicemarks, registered trademarks, and registered servicemarks are the property of their respective owners.